Student team: NO
CORE is a web application framework written at PNNL primarily by me using open source software like MySQL and PHP that allows users to easily interface with underlying data and define different types of views easily. Pulling data into CORE tables is easily done, and defining the views of the data is done with a simple interface that allows for complex joins and styles. Views can be maps, timelines, and tables, and can be editable, allowing the user to change the data if necessary. The views can interact with each other, giving the user the ability to see a map and table and timeline side by side, and all viewing the same data in different ways.
Two Page Summary: NO
Grid cell number of where the device went off (91x61):
52x28 at time 375, but something else was happening at 54x17 around time 550
Short Answer:
Shortly after the event, 18, 19, 36, 50, 56, and 76 stopped moving and remained stationary.
This is not the only interesting time period, though. About two minutes after the event and while people were evacuating, there was something happening in the vicinity of 54x17. Several people traveled by that area, some at the same time, and stopped moving shortly after, never making it all the way to the evacuation area. Other people who had passed through that area prior to 550 did not have a problem evacuating.
Notice that from the time period 550 to the end some people were already evacuating and made it out fine. Others didn't ever make it through.
Third, shortly after the event in the vicinity of 19x43 there was a large crowd, with some people moving back and forth, but ultimately everybody from there made it to the evacuation area.
List of RFID tag numbers :
1; 21; 36; 39; 56; 73; 80
Short Answer:
1 was the only other one to get to the East room and may have seen suspect 21
21 might have escaped, but also oddly was evacuating well before the incident and was leaving the scene where the event seems to have taken place. Further, his path indicates something odd; he was only traveling in straight lines. Traveling through a vent, perhaps?
36 is either a casualty or a suspect. His badge doesn't move at all, indicating he was either dead or had left his badge at that location.
39 is highly suspicious because his path indicates that he went through walls. Possible explanations are traveling above the ceiling or below the floor, or errors in the RFID tracking.
Further, he didn't make it past the secondary event at 54x17.
56 was moving towards the site well before the incident. Once it started, he moved very little, so either he was involved, or he was unfortunately walking through the hallway at the wrong time.
73 walked right by casualty 36
80 also walked right by casualty 36. Since 36 never moves, and nobody even pauses by him, perhaps 36 wasn't wearing his badge. He made it past the odd area at 54x17 just prior to time 550 and even walked towards it, so he may have been responsible for whatever started it.
Note: casualties aren't included, though they may still be alive. If any of them survived, they would be potential witnesses.
List of RFID tag numbers :
21; 28; 29; 44; 80
Short Answer:
21 was very odd. He started off at the site of the event, then only moved in straight lines. At the end he was in a walled space. He is the most suspect of everyone.
28 during the evacuation ventured towards the incident at first, then turned around and escaped to another area. He might have seen something to cause his about-face.
29 was moving before the incident. It's probably coincidence, but he was one of few people who were moving before anything happened.
44 same as 29. She was one of only a few people moving before the incident. Since she was already really close to an exit, however, it is highly likely this was only coincidence, so only a quick check for an alibi would be warranted.
80 walked right by the secondary event just prior to 550 and paced a little before continuing on outside. He may have seen something odd or placed something.
List of RFID tag numbers:
18; 19; 36; 39; 47; 50; 56; 59; 60; 65; 69; 76; 78
Short Answer:
18 Didn't move very much at all after the incident. PRIMARY
19 Started to evacuate, but stopped short. PRIMARY
36 Never moved. Either he was a casualty or his badge was left there. ODD
39 Walked through walls but didn't make it past the secondary event. SECONDARY
47 Got caught up in the secondary event and never made it out. SECONDARY
59 Was evacuating just fine, but turned around and went the wrong way along the wall, eventually stopping halfway from both exits. Maybe not a casualty, but she didn't evacuate, and she did stop moving. ODD
60 Was evacuating but couldn't quite make it into the large evacuation area. SECONDARY
65 Was also evacuating but interacted with 60 at around point 555, and then both of them only moved a little. SECONDARY
69 Was evacuating but got caught in the secondary event, and then only moved a little. SECONDARY
76 Didn't make it far from the office. Around 380 she tried to evacuate but didn't make it outside the office. PRIMARY
78 Got to the secondary event late but didn't go far after he got there. SECONDARY
Detailed Answer:
To solve this problem, I needed to develop a special tool in CORE that would visualize the map and place the people on it. I imported the data into a CORE database table and wrote the tool to visually display the graph with sliders for selecting the time range and a select box for choosing the people to visualize. Then it was just a matter of looking at the people move over time and picking out odd trails and setting the time range to view movement of people at specific times. The included video shows the use of the tool to explore interesting aspects of the evacuation.
Shortly before the event, Ramon (21) was making odd movements near 52x28, only going in straight lines. The event started at about time point 375. Then most people left their offices for the exits, except for those in the vicinity of 52x28. People went fairly directly to the Northwest and Southeast corners of the largest rooms in the perimeter of the building.
The following graph shows everybody's movement prior to 375. Notice the strange and perfectly straight movements by Ramon (in blue).
In the 20 seconds after the incident, almost everybody had started to evacuate.
Most people made it safely to the evacuation areas. There was a large group of people who went through the hallway at 19x43, leading to what may have been a scuffle or mob. People had a delay getting through that area.
Something else happened over at 54x17 during the evacuation around time 550. Some people made it to the evacuation room before this time, but after it people did not and many people stopped moving in that area.
This graph is of people towards the end of the time period. Notice that some are stationary outside of the evacuation area, while others had evacuated to the bottom right and were still moving around slightly. See the earlier graph showing that only people who had passed the door by 550 successfully evacuated.
Phil Marin (39) is odd because it appears his track goes through walls. I have no explanation for this other than that he travelled above or below the walls.
Ramon Katalanow (21) is also odd because he only travels in straight lines, his movement is before the event, and he appears to be inside a wall at the end. I suspect that he was crawling in ducts during this period.
During this challenge I compiled an interesting people list. Most of them I have addressed throughout the description of this event. Here is a summary:
Interesting people list:
1; only one who evacuated to the East room and may have seen suspect 21
3; was near the secondary event just prior to 550 and evacuated safely
4; there might just be something wrong with the data, but his track goes slightly through walls
13; had an odd pacing back and along most of the lenght of the north room before entering it
18; casualty of main event
19; casualty of main event
20; same as 3: near secondary event just prior and evacuated safely
21; was near primary event before it happened, and only traveled in straight lines
28; backtracked twice during evacuation. Once was near primary event. Also paused near secondary event.
29; was moving before the event. likely just coincidence.
36; never moved at all. either he was a casualty or he left his badge there.
39; travelled through walls, didn't make it past secondary event.
47; casualty of secondary event. looks like she tried to move away from it at first.
50; casualty of main event
51; was at location of secondary event when it happened
56; casualty of main event
59; like 13, had an odd trail along north wall, and never made it out. Ended up halfway away from both exits.
60; casualty of secondary event.
65; casualty of secondary event.
69; casualty of secondary event.
76; casualty of main event
78; casualty of secondary event.
80; was near the secondary event just prior to 550 and evacuated safely